Skip to content

HIP-1398: TSS ceremony - #1398

Merged
mgarbs merged 13 commits into
hiero-ledger:mainfrom
rsinha:tss-ceremony
Mar 25, 2026
Merged

HIP-1398: TSS ceremony#1398
mgarbs merged 13 commits into
hiero-ledger:mainfrom
rsinha:tss-ceremony

Conversation

@rsinha

@rsinha rsinha commented Feb 4, 2026

Copy link
Copy Markdown
Contributor

Description:
This HIP specifies the TSS ceremony operations, which is necessary to perform TSS operations (as specified in HIP-1200).

rsinha and others added 7 commits January 20, 2026 17:53
Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
…des, not

 signing laptops (which do not have reliable networking and may not be powered
 on for more than a few minutes at a time).

Signed-off-by: Joseph S. <121976561+jsync-swirlds@users.noreply.github.com>
Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
@rsinha
rsinha requested a review from a team as a code owner February 4, 2026 17:46
@rsinha rsinha changed the title HIP-xyz: Tss ceremony HIP-1398: Tss ceremony Feb 4, 2026
Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
@rsinha rsinha changed the title HIP-1398: Tss ceremony HIP-1398: TSS ceremony Feb 4, 2026
@mgarbs mgarbs moved this to Draft in HIP Tracker Feb 18, 2026
Comment thread HIP/hip-1398.md
Comment thread HIP/hip-1398.md Outdated
Comment thread HIP/hip-1398.md
Comment thread HIP/hip-1398.md Outdated
Comment thread HIP/hip-1398.md Outdated

@jsync-swirlds jsync-swirlds left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for putting this together.
Just a few minor comments.

Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
jsync-swirlds
jsync-swirlds previously approved these changes Feb 25, 2026
@mgarbs mgarbs moved this from Draft to Last Call in HIP Tracker Feb 27, 2026
@mgarbs mgarbs moved this from Last Call to Review in HIP Tracker Feb 27, 2026
@mgarbs mgarbs mentioned this pull request Feb 27, 2026
@mgarbs mgarbs moved this from Review to Last Call in HIP Tracker Mar 4, 2026

@Neurone Neurone left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest this change for the HIP to highlight we can potentially include selected community members in the TSS ceremony process.

Comment thread HIP/hip-1398.md
Signed-off-by: Giuseppe Bertone <giuseppe.bertone@proton.me>
Comment thread HIP/hip-1398.md Outdated
Signed-off-by: Joseph S. <121976561+jsync-swirlds@users.noreply.github.com>
Signed-off-by: Michael Garber <michael.garber@hashgraph.com>
mgarbs
mgarbs previously approved these changes Mar 5, 2026
@dmueller2001

Copy link
Copy Markdown

The link to the Hedera Cryptography repository for the reference implementation is broken, is this not yet a public repo? @rsinha

Signed-off-by: Michael Garber <michael.garber@hashgraph.com>
@dmueller2001

Copy link
Copy Markdown

Request for further governance / participation clarification

The HIP states that the ceremony will be executed by “the council members — specifically, those council members that also run consensus nodes.” However, the participation model is not fully specified. It would be helpful to clarify the intended governance and participation requirements for the ceremony.

In particular:

  • Is participation expected from all eligible council members running consensus nodes, or is participation optional?
  • Is there a minimum number of contributors required for the ceremony to be considered valid?
  • What happens operationally if some eligible participants decline or are unavailable during the ceremony window?
  • Are contributors limited strictly to council-operated nodes, or can additional participants contribute entropy?
  • Is there a role for independent observers or auditors in verifying the ceremony transcript?

Since the security model relies on the assumption that at least one participant contributes honest randomness and deletes their secret material, clearly specifying the eligibility and quorum expectations for contributors would strengthen the operational clarity of the proposal.

Additionally, it would be helpful to clarify how this ceremony applies to third-party deployments of a Hiero-ledger–based network.

For example:

  • If an organization deploys its own (possibly private) network based on Hiero Ledger, is running a TSS ceremony required?
  • Can such deployments reuse the parameters generated by this ceremony, or are they expected to run their own ceremony?
  • If they must run their own ceremony, what guidance or tooling is expected to support that process?

Clarifying the intended model for downstream or private deployments would help ensure that the specification is usable by implementers beyond the initial network environment.

@rsinha

rsinha commented Mar 5, 2026

Copy link
Copy Markdown
Contributor Author

The link to the Hedera Cryptography repository for the reference implementation is broken, is this not yet a public repo? @rsinha

It is not yet public. We are working towards making it public.

@jsync-swirlds

jsync-swirlds commented Mar 5, 2026

Copy link
Copy Markdown
Contributor

Request for further governance / participation clarification

  • Is participation expected from all eligible council members running consensus nodes, or is participation optional?

The consensus node servers will run the software autonomously. Participation means letting their servers run as normal.

  • Is there a minimum number of contributors required for the ceremony to be considered valid?

As long as at least 1 honest entity participates in the ceremony, the result is valid.
We will rerun the ceremony if we do not have results from more than 1/3 of active nodes.

  • What happens operationally if some eligible participants decline or are unavailable during the ceremony window?

The software automatically times out if a prior node does not produce output and continues the ceremony without that node.

  • Are contributors limited strictly to council-operated nodes, or can additional participants contribute entropy?

We are looking into options for a selected number of additional participants. @Neurone is working on that process.

  • Is there a role for independent observers or auditors in verifying the ceremony transcript?

Yes, all inputs and outputs will be public and independent observers are welcome and encouraged to verify the integrity and validity of the result.

  • If an organization deploys its own (possibly private) network based on Hiero Ledger, is running a TSS ceremony required?
  • Can such deployments reuse the parameters generated by this ceremony, or are they expected to run their own ceremony?
  • If they must run their own ceremony, what guidance or tooling is expected to support that process?

This should be clear in the text (if not, we need to add this). All Hiero networks can use the output of this one ceremony without any reduction in cryptographic quality or security. There is no requirement nor expectation that any entity will repeat this ceremony.
Any given Hiero network could choose to run the ceremony, and I agree that we should provide some helpful documentation to assist in that if anyone wishes to do so. That's beyond the scope of the HIP, but I'll bring that suggestion to the team for follow-up.

@mgarbs
mgarbs merged commit 7ccca23 into hiero-ledger:main Mar 25, 2026
7 of 9 checks passed
@github-project-automation github-project-automation Bot moved this from Last Call to Withdrawn in HIP Tracker Mar 25, 2026
@mgarbs mgarbs moved this from Withdrawn to Last Call in HIP Tracker Apr 6, 2026
@mgarbs mgarbs removed this from HIP Tracker Apr 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants